Skip to content

Conversation

@jfroche
Copy link
Collaborator

@jfroche jfroche commented Nov 6, 2025

pg_upgrade may generate an update_extensions.sql script to update extensions after a major version upgrade.
This PR modifies the extension tests to check for the presence of this script after upgrading PostgreSQL to version 17.
If the script exists, it is executed to ensure that the extensions are updated correctly.

@jfroche jfroche marked this pull request as ready for review November 6, 2025 17:20
@jfroche jfroche requested review from a team as code owners November 6, 2025 17:20
@jfroche jfroche force-pushed the fix/nixos-test-update-after-pg-upgrade branch 2 times, most recently from 28b6e73 to 1a9394d Compare November 10, 2025 11:04
…n the extension tests

pg_upgrade may generate an update_extensions.sql script to update extensions after a major version upgrade. 
This commit modifies the extension tests to check for the presence of this script after upgrading PostgreSQL to version 17. 
If the script exists, it is executed to ensure that the extensions are updated correctly.
Thanks to the improvement related to the generated pg_upgrade script, we can now reuse the generic postgres extension test for postgis.
This helps us identify why certain extensions do not use the generic tests.
@yvan-sraka yvan-sraka force-pushed the fix/nixos-test-update-after-pg-upgrade branch from 1a9394d to cecd0ca Compare November 17, 2025 09:46
@yvan-sraka yvan-sraka self-assigned this Nov 17, 2025
@yvan-sraka yvan-sraka requested a review from samrose November 17, 2025 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants